Configuring the RelativeCacheSize setting

The AutoManager EDM Server service caches each vault’s database in memory to optimize performance. The more memory that is available, the more data (up to the entire database) can be cached and the better the performance will be. The RelativeCacheSize setting is used by the system to determine the maximum amount of server memory (expressed as a percentage of the vault database size) that should be used for the vault’s database cache.  We recommend a setting of 100 (percent) if enough application memory is available but depending on the size of the vault database, it is sometimes not possible because there is not enough memory available on the server. For SQL Server vaults, the database cache size should be at most 50% of the database file size. For Oracle vaults, the database cache size should be 100% of the database file size. If multiple vaults are used, the available server memory should be divided between caches of all vaults according to their database file size.

Note    This cache is in addition to the caching performed by SQL Server or Oracle if either program is used.

If the amount of installed RAM on the server cannot accommodate optimum cache sizes for all vaults, we recommend installing additional memory in the server computer, if possible. If the computer has already been configured with its maximum amount of memory, we recommend that you consider either reducing this setting, configuring the High Performance Option as described in Configuring the High Performance Option or the other recommendations described in Optimizing the server operating system. and Optimizing the Meridian server software.

This setting works together with the MaximumCacheSize setting. The system will use whichever setting results in a smaller cache size. For example, specified 1 GB of RAM available for caching and a 750 MB database file size, setting MaximumCacheSize to 1000 (MB) and RelativeCacheSize to 100 (percent) will initially result in the entire database being cached because 100 percent of 750 MB is less than 1000 MB. The RelativeCacheSize setting is in effect and is controlling the cache size. However, the database will grow over time with the addition of more documents, revisions, and so on and will consume more memory accordingly. When the database size exceeds 1000 MB in size, the MaximumCacheSize setting will come into effect and limit the cache size to 1000 MB because 100 percent of anything over 1000 MB is greater than 1000 MB. If additional memory is made available for caching, the MaximumCacheSize setting should be adjusted upward so that the RelativeCacheSize setting becomes the effective setting again. Both settings should be considered together with the amount of installed RAM and the number of active vaults.

Note    If the Meridian High Performance Option is used, this setting is ignored as described in Configuring the High Performance Option.

Note    This setting is overridden if the HyperCache setting is enabled as described in Configuring HyperCache.

To configure the RelativeCacheSize setting:

1. In Administrator, click EDM Server in the left pane. The list of active vaults appears in the right pane.
2. Select the vault that you want to configure in the right pane.
3. On the Action menu and select Properties. The vault’s Properties dialog box appears.
4. Click the Advanced button. The Advanced Vault Properties dialog box appears.
5. Adjust the RelativeCacheSize setting and click OK.

This setting can also be configured with the RelativeCacheSize registry key located at:

HKEY_LOCAL_MACHINE\SOFTWARE\Cyco\AutoManager Meridian\CurrentVersion\Installed DataStores\<VaultName>\CompoundItemService\RelativeCacheSize